I have SBS2008 installed (and fully updated), as well as Exchange 2007 (sp3). I am attempting to connecting an Apple Mail client (Snow Leopard) to my Exchange Server. By way of observing wire-traces, using my browser, and noting a distinct LACK of reference to anything related to Web Services, I have come to the conclusion that EWS is not up and running. I have found several posts related to fine-tuning, and configuring web-services, but many of the configuration tabs, and tree-nodes, and command-line tools either are absent, different, or simply fail. My previous attempts are far too numerous to catalog here (nor have I been particularly diligent about recording them). Any help would be appreciated, given that I'm right about at that point where taking a baseball bat to my monitor while making vile statements about the Microsoft Development team is starting to sound like a good idea. thanks, George

Can you find the requests for EWS in the server's IIS log file? If so, can you post the lgged lines?Outlook Web Access For PDA , OWA For WAP www.owa-pda.com email a@t leederbyshire d.0.t c.0.m

The only log file I was able to find (c:/windows/system32/logfiles/httperr/httperr1.txt) does not contain anything related to any attempts (ie. find:owa, ews, EWS all fail). My site-tree in IIS contains but one site: ftp sites. My EMS indicates that OWA is as installed and active as the present check-boxes seem to permit. Server manager indicates that IIS is running. My web browser shows the default welcome screen for IIS on port 80, but /owa, /ews/ and /EWS all fail. My SBS console contradicts the IIS manager by stating that OWA is both installed and "Online". Nothing, anywhere, mentions exchange web services...Except for the box that exchange 2007 came in. thanks for your help. -George

I have a *partial* solution to the problem. https. By default Apple Mail and Entourage both operate using http on port 80, whereas EWS and OWA, by default, operate using https on port 443. Now the trick is to figure out where to tell it to operate over http on 80. Give that *nothing* in the settings seems to indicate the existence of EWS let alone its configuration...this could get interesting.

After logging in once over https, IIS manager now shows a 'Sites' node and 'Application Pools' node whereas it used to only show the 'FTP Sites' node (apparently Microsoft only lets you manage sites that have been accessed via a web-browser...because that makes sense...pay no attention to the man behind the curtain). The service is, by default, enabled for Http (note that the manager is inconsistent with capitaLIZATION, though consistency does not seem to make a difference). Despite being enabled on http, and even restarting IIS, it still serves 404's when attempting to access over an insecure connection. -George

This is getting confusing. I suppose it's my own fault for not answering for so long, but I think I must be in a different time zone to you. Anyway, if you see differences in behaviour between http and https, this sometimes means that there are several web sites on the server, and that one or more is configured with a host header name. Host headers don't work with SSL, so what you see when you use https might come from a different site on the same server compared to what you saw when you used http. I'm still not sure from the above posts whether or not you've tried using IIS Manager to see if the EWS VDir is actually present under the default web site. Assuming that logging is enabled for the default web site, the log files should be in C:\Windows\System32\LogFiles\W3SVC1 Are you sure that you have the EWS version of Entourage? Out of the box, it still uses WebDAV, and you have to specifically download the EWS version. At least, that was the situation when I installed it a few weeks ago. I don't know what protocol Apple Mail uses with Exchange. It could be something as simple as IMAP.Outlook Web Access For PDA , OWA For WAP www.owa-pda.com email a@t leederbyshire d.0.t c.0.m

Please, no reason for apologies. I've included the three major topics of interest below: Current Question, Chronological History, and Cheap Shots at Microsoft. Any help is, as usual, greatly appreciated. thanks, George == Current Question == My current issue (aside from how to make Blackberry Enterprise Server work) is how to get Microsoft Exchange Web Services to work via HTTP on port 80. == Chronological History == * Installed SBS2008 * SBS refused, initially, to "connect to the internet" because there was a DHCP server on my network. * I installed Exchange 2007 * I installed all available updates to both SBS2008 and Exchange 2007 (SP3) * Checked the following locations for any reference to EWS: IIS Management Console, SBS Console, Exchange management console * IIS Management showed exactly one configured site: FTP Sites * I created a new exchange profile in MS Entourage, which did not work * I created a new exchange profile in Apple Mail, which did not work * I tried searching the hard drive for Exchange.asmx * I tried using OWA (which was listed as enabled in the Exchange Management Console), which did not work * A friend of mine recommended I try to access OWA over https on port 443...it worked * After successfully accessing OWA, I tried switching my Entourage profile to use SSL, it worked * After successfully accessing EWS via Entourage, several site-nodes magically appeared in the IIS manager. * I navigated every node in the path to EWS ensuring that HTTP on port 80 was enabled, which did not yield any results. * I tried ensuring that the inconsistent caPitaliZation windows ships with was corrected and made consistent, which did not yield any results. == Cheap Shots at Microsoft == * As we all know, computers are incapable of connecting to the internet whenever a DHCP server is present on the network; after all, preventing network connectivity is what DHCP servers are for...oh...wait...it's the OPPOSITE of that...Go Microsoft! * My fingers may have typed HTTP and 80, but my eyes said HTTPS and 443...Go Microsoft! * SBS enforces the wise policy of preventing any kind of configuration changes to a web service BEFORE one of your CLIENTS has accessed it...Go Microsoft!

So, at the moment, you can access EWS using SSL, but not without? It also sounds like you can now see the EWS VDir in IIS Manager? Have you checked to see if SSL is required on it? I know that sounds basic, so please bear with me, but I don't specifically see it mentioned above. It's not as immediately obvious as it was in previous versions of IIS.Outlook Web Access For PDA , OWA For WAP www.owa-pda.com email a@t leederbyshire d.0.t c.0.m